Method for monitoring PDCCH, terminal and network device

ABSTRACT

A method for monitoring a PDCCH, a terminal and a network device are provided. The method includes: determining configuration information of at least one control resource set (CORESET); and transmitting the configuration information of the at least one CORESET to a terminal; where the at least one CORESET is configured per carrier or per bandwidth part (BWP), and the carrier comprises at least one BWP. In a case that the at least one CORESET is configured per carrier, one carrier is configured with at least one CORESET; and in a case that the at least one CORESET is configured per BWP, one BWP is configured with at least one CORESET.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is a 35 USC § 371 U.S. national stage ofInternational Application No. PCT/CN2018/098290 filed on Aug. 2, 2018,which claims a priority to Chinese Patent Application No. 201710687280.1filed on Aug. 11, 2017, which are incorporated in their entireties byreference herein.

TECHNICAL FIELD

The present disclosure relates to the technical field of wirelesscommunications, and in particular to a method for monitoring a PDCCH, aterminal and a network device.

BACKGROUND

In the 5^(th) Generation (5G) mobile communication system, a highbandwidth (for example, 100 MHZ or more) is usually used to transmitdata. Terminals have different bandwidth capabilities. In order toenable terminals with low bandwidth capabilities to access a part of thebandwidth in a high bandwidth network, the concept of bandwidth part(BWP) is introduced into a new radio (NR) system. In the NR system, oneor more BWPs can be configured for a terminal, and when multiple BWPsare configured for a terminal, the BWPs can adopt a same numerology ordifferent numerologies, so that the terminal can access a BWP of a highbandwidth network. For a scenario where a network device configures oneor more BWP for one terminal, the issue of PDCCH monitoring by theterminal has not been discussed accordingly.

SUMMARY

In a first aspect, the present disclosure provides a method formonitoring a physical downlink control channel (PDCCH), which is appliedto a network device and includes:

determining configuration information of at least one control resourceset (CORESET); and

transmitting the configuration information of the at least one CORESETto a terminal, where the at least one CORESET is configured per carrieror per bandwidth part (BWP), and the carrier includes at least one BWP,

where in a case that the at least one CORESET is configured per carrier,one carrier is configured with at least one CORESET; and in a case thatthe at least one CORESET is configured per BWP, one BWP is configuredwith at least one CORESET.

In a second aspect, the present disclosure provides a method formonitoring a PDCCH, which is applied to a terminal and includes:

receiving configuration information of at least one control resource set(CORESET), where the at least one CORESET is configured per carrier orper bandwidth part (BWP), and the carrier includes at least one BWP; ina case that the at least one CORESET is configured per carrier, onecarrier is configured with at least one CORESET; and in a case that theat least one CORESET is configured per BWP, one BWP is configured withat least one CORESET; and

monitoring the PDCCH in the at least one CORESET in accordance with theconfiguration information of the at least one CORESET.

In a third aspect, the present disclosure provides a network device,which includes:

a determination unit, configured to determine configuration informationof at least one control resource set (CORESET); and

a transmission unit, configured to transmit the configurationinformation of the at least one CORESET to a terminal; where the atleast one CORESET is configured per carrier or per bandwidth part (BWP),and the carrier includes at least one BWP,

where in a case that the at least one CORESET is configured per carrier,one carrier is configured with at least one CORESET; and in a case thatthe at least one CORESET is configured per BWP, one BWP is configuredwith at least one CORESET.

In a fourth aspect, the present disclosure provides a terminal, whichincludes:

a reception unit, configured to receive configuration information of atleast one control resource set (CORESET), where the at least one CORESETis configured per carrier or per bandwidth part (BWP), and the carrierincludes at least one BWP; in a case that the at least one CORESET isconfigured per carrier, one carrier is configured with at least oneCORESET; and in a case that the at least one CORESET is configured perBWP, one BWP is configured with at least one CORESET; and

a monitoring unit, configured to monitor a physical downlink controlchannel (PDCCH) in the at least one CORESET in accordance with theconfiguration information of the at least one CORESET.

In a fifth aspect, the present disclosure provides a terminal. Theterminal includes a processor, a memory, and a program that is stored onthe memory and executable on the processor. When executing the program,the processor is configured to perform steps of the method formonitoring a PDCCH provided in the first aspect.

In a sixth aspect, the present disclosure provides a computer-readablestorage medium. The computer-readable storage medium stores a program,and the program is executed by a processor to perform steps of themethod for monitoring a PDCCH provided in the first aspect.

In a seventh aspect, the present disclosure provides a network device,which includes a processor, a memory, and a program that is stored onthe memory and executable on the processor. When executing the program,the processor is configured to perform steps of the method formonitoring a PDCCH provided in the second aspect.

In an eighth aspect, the present disclosure provides a computer-readablestorage medium, on which a program is stored. The program, whenexecuted, configures a processor to perform steps of the method formonitoring a PDCCH provided in the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to illustrate technical solutions of embodiments of the presentdisclosure more clearly, drawings used in the description of theembodiments of the present disclosure are briefly described below.Obviously, the drawings in the following description are only someembodiments of the present disclosure, and for a person of ordinaryskill in the art, other drawings can be obtained based on these drawingswithout creative efforts.

FIG. 1 is an architecture diagram of a communication system to whichtechnical solutions are applicable according to an embodiment of thepresent disclosure;

FIG. 2 is a schematic diagram of a BWP scenario according to anembodiment of the present disclosure;

FIG. 3 is another schematic diagram of a BWP scenario according to anembodiment of the present disclosure;

FIG. 4 is another schematic diagram of a BWP scenario according to anembodiment of the present disclosure;

FIG. 5 is a schematic flowchart of a method for monitoring a PDCCHaccording to an embodiment of the present disclosure;

FIG. 6 is another schematic flowchart of a method for monitoring a PDCCHaccording to an embodiment of the present disclosure;

FIG. 7 is another schematic diagram of a BWP scenario where a CORESET ismonitored according to an embodiment of the present disclosure;

FIG. 8 is another schematic diagram of a BWP scenario where a CORESET ismonitored according to an embodiment of the present disclosure;

FIG. 9 is another schematic diagram of a BWP scenario where a CORESET ismonitored according to an embodiment of the present disclosure;

FIG. 10 is another schematic diagram of a BWP scenario where a CORESETis monitored according to an embodiment of the present disclosure;

FIG. 11 is another schematic flowchart of a method for monitoring aPDCCH according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 13 is another schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 14 is another schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 15 is another schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 16 is another schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 17 is another schematic diagram of a BWP switching scenario where aCORESET is monitored according to an embodiment of the presentdisclosure;

FIG. 18 is a schematic structural diagram of a terminal according to anembodiment of the present disclosure;

FIG. 19 is another schematic structural diagram of a terminal accordingto an embodiment of the present disclosure;

FIG. 20 is a schematic structural diagram of a network device accordingto an embodiment of the present disclosure; and

FIG. 21 is another schematic structural diagram of a network deviceaccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Exemplary embodiments of the present disclosure will be described belowin more detail with reference to the accompanying drawings. Although theexemplary embodiments of the present disclosure are shown in thedrawings, it should be understood that the present disclosure can beimplemented in various forms and should not be limited by theembodiments set forth herein. On the contrary, these embodiments areprovided to enable a thorough understanding of the present disclosure,and to fully convey the scope of the present disclosure to those skilledin the art.

The technical solutions provided by the present disclosure can beapplied to various communication systems, for example, 5^(th) Generation(5G) communication systems, future evolution systems, or multiplecommunication convergence systems, and can be applied in a variety ofapplication scenarios, for example, machine-to-machine (M2M),device-to-device (D2D), macro communication, enhanced mobile Broadband(eMBB), ultra reliable and low latency communication (uRLLC) and massivemachine type communication (mMTC). These scenarios include, but notlimited to, communication between a terminal and a terminal, orcommunication between a network device and a network device, orcommunication between a network device and a terminal. The embodimentsof the present disclosure can be applied to communications among networkdevices and terminals in a 5G communication system, or communicationsamong terminals and terminals in a 5G communication system, orcommunications among network devices and network devices in a 5Gcommunication system.

FIG. 1 shows a schematic diagram of an optional structure of acommunication system according to an embodiment of the presentdisclosure. As shown in FIG. 1, the communication system includes atleast one network device 100 (only one is shown in FIG. 1) and one ormore terminals 200 connected to each network device 100. The networkdevice 100 may be a base station, a core network device, a transmissionreference point (TRP), a relay station, or an access point. The networkdevice 100 may be: a base transceiver station (BTS) in a global systemfor mobile communication (GSM) or a code division multiple access (CDMA)network, or a NodeB (NB) in a wideband code division multiple access(WCDMA), or an eNB or an evolutional NodeB (eNodeB) in LTE. The networkdevice 100 may also be a wireless controller in a cloud radio accessnetwork (CRAN) scenario. The network device 100 may also be a networkdevice in a 5G communication system or a network device in a futureevolved network, and may also be a wearable device or a vehicle-mounteddevice.

The terminal 200 may be a wireless terminal or a wired terminal. Thewireless terminal may be a device that provides data connectivity ofvoice and/or other services to a user, a handheld device with a wirelesscommunication function, a computing device, or other processing devicesconnected to a wireless modem, a vehicle-mounted device, a wearabledevice, a terminal in a future 5G network, or a terminal in a futureevolved public land mobile network (PLMN) network. A wireless terminalmay communicate with one or more core networks over a radio accessnetwork (RAN). The wireless terminal may be a mobile terminal such as amobile phone (also referred to as a “cellular” phone) and a computerwith a mobile terminal, which, for example, may be a portable,pocket-size, handheld, computer-built or vehicle-mounted mobile device.The wireless terminal exchanges language and/or data with a wirelessaccess network, and may include a personal communication service (PCS)phone, a cordless phone, a session initiation protocol (SIP) phone, awireless local loop (WLL) station, a personal digital assistant (PDA),and other devices. The wireless terminal may also be: a mobile device, auser equipment (UE), a UE terminal, an access terminal, a wirelesscommunication equipment, a terminal unit, a terminal station, a mobilestation, a remote station, a remote terminal, a subscriber unit, asubscriber station, a user agent, a terminal device, etc. The forgoingis just as an example, and a terminal is not limited to thereto inpractical applications.

Some terms involved in the present disclosure are explained below forunderstanding of readers.

1. Control Resource Set (CORESET)

CORESET is a type of time-frequency resource set introduced in NR, thatis, a terminal performs physical downlink control channel (PDCCH)detection at a corresponding CORESET. CORESET includes a set of resourceelement groups (REGs).

For example, configuration information of a CORESET may be notified inat least one of the following manners:

configuration information of the CORESET being notified throughhigh-layer signaling; or

configuration information of the CORESET being transmitted via abroadcast channel, system information, and the like; or

configuration information of the CORESET being predefined based on oneor more pieces of information such as a system bandwidth, a subcarrierspacing, an antenna configuration, or a carrier frequency.

The configuration information of a CORESET in the present specificationincludes, but not limited to, at least one piece of the followinginformation: time-frequency resource information of the CORESET, and aset of aggregation levels at which a PDCCH requires to be blindlydetected in the CORESET, the number of PDCCH candidate resources onwhich a PDCCH requires to be blindly detected in the CORESET at eachaggregation level, or a DCI parameter (a DCI format or a length of DCI)of a PDCCH requiring to be blindly detected in the CORESET. Thetime-frequency resource information of a CORESET includesfrequency-domain resource information of the CORESET (such as the numberof PRBs, and a time-frequency position), and time-domain resourceinformation (such as the number of OFDM symbols).

2. Bandwidth Part (BWP)

A terminal can be configured with one or more BWPs, and when multipleBWPs are configured for a terminal, the BWPs can adopt a same numerologyor different numerologies. Generally, a position of a BWP in a carriermay be determined by a center frequency of the BWP.

The solutions provided by the present disclosure is mainly applied in ascenario where a network device configures one or more BWPs for aterminal. Some BWP application scenarios are given below.

In a first scenario, as shown in FIG. 2, a terminal accesses a BWP of asystem bandwidth.

In a second scenario, as shown in FIG. 3, a BWP for a terminal isadjusted, a center frequency of the BWP is unchanged, and a bandwidth ofthe BWP is changed.

In a third scenario, as shown in FIG. 4, a terminal accesses two BWPs ina system bandwidth, and the two BWPs have different numerologies.

Exemplarily, a downlink BWP and an uplink BWP for a terminal can beconfigured by a network device, respectively.

Exemplarily, one BWP (specified by Rel-15 technical specification) ormultiple BWPs (specified by a technical specification in a laterrelease) may be configured for a terminal.

Exemplarily, a terminal may perform BWP adjustment based on indicationof Layer 1 (L1) signaling or Layer 2 (L2) signaling transmitted by anetwork device, which includes any of the following cases:

in a first case, a center frequency of a BWP is unchanged, and abandwidth of the BWP changes, where it should be noted that RF retuningis not required in the first case; or

in a second case, a center frequency of a BWP changes, and a bandwidthof the BWP is unchanged; or

in a third case, a center frequency of a BWP changes, and a bandwidth ofthe BWP changes.

3. Downlink Control Information (DCI)

In a LTE system, a physical downlink control channel (PDCCH) istransmitted in a downlink sub-frame, and the PDCCH and a physicaldownlink shared channel (PDSCH) are in a time division multiplexing(TDM) relation. The PDCCH is transmitted through the first to the thirdorthogonal frequency division multiplexing (OFDM) symbols of a downlinksub-frame. Specifically, as shown in FIG. 1, generally, a control regionfor transmitting a PDCCH in the LTE system (that is, the first to thethird subcarriers of a downlink sub-frame) is composed of logicallydivided CCEs. A basic unit of a time-frequency resource of a DCI carriedon the PDCCH is also a control channel element (CCE). DCI can betransmitted at different aggregation levels (ALs). The aggregation levelrefers to the number of CCEs that carry a DCI. The aggregation level maybe, for example but not limited to: 1, 2, 4, 8, 16, and 32. For example,an aggregation level of 2 means that a DCI is carried on 2 CCEs.

For example, a CCE includes, but not limited to, 6 resource elementgroups (REGs). The 6 REGs may be constructed in a concentrated ordistributed way when constructing a CCE, which is not limited herein. Byway of example, 12 consecutive REs (which does not include a RE occupiedby a reference signal) constitute one REG. RE is the smallesttime-frequency resource unit. RE may be uniquely identified by an indexpair (k,l), k is an index of a subcarrier, and l is an index of asymbol.

4. Blind Decoding

As described above, a DCI can be transmitted in the first to the thirdsymbols of a sub-frame, and a DCI can be transmitted at differentaggregation levels. However, since the PDCCH is a signaling transmittedby the base station, and the UE has not received any other informationexcept some system information before this transmission, the UE does notknow the number of CCEs, a location of a CCE, a DCI format fortransmitting a CCE, or an aggregation level of the DCI. Therefore, theUE needs to detect possible time-frequency resource locations of the DCIand possible aggregation levels of the DCI through blind detection, soas to receive the DCI. That is, a UE monitors a PDCCH transmitted by thebase station by using a blind detection method to obtain the DCI.

It should be noted that the UE needs to blindly detect a control channelin every non-DRX (discontinuous reception) downlink sub-frame.

In order to reduce the complexity of blind detection of a UE, two searchspaces are defined in the LTE system, namely a common search space (CSS)and a UE-specific search space (UESS). The size of a search space usesthe number of CCEs as a unit. CSS is mainly used to transmit DCI forscheduling cell-specific control information (for example, systeminformation, paging messages, and multicast power control information),and search needs to be performed for each user. UESS is mainly used totransmit a DCI for resources scheduling for each UE. For a CSS, the CSSincludes the first 16 CCEs in each downlink sub-frame, and anaggregation level of a PDCCH may be 4 or 8. Therefore, when a usersearches a common search space, the user searches for four timesstarting from CCE 0 and according to an AL of 4, and then searches twiceat an AL of 8. For a UCSS, since a starting position of a CCE of theUCSS of each UE in a downlink sub-frame is related to a sub-frame numberor the RNTI of the UE, etc., starting points of various UEs for searchare different, that is, a PDCCH aggregation level can be 1, 2, 4, or 8in UCSS. That AL is equal to 1 refers to performing search for sixtimes, that AL is equal to 2 refers to performing search for six times,that AL is equal to 4 refers to performing search twice, and that thatAL is equal to 8 refers to performing search twice.

In view of the above, if the number of blind detections is representedbased on an aggregation level being L, it is specified in the LTE thatfor UCSS, when L={1, 2, 4, 8}, the number of blind detections is {6, 6,2, 2}; and for CSS, When L={4, 8}, the number of blind detections is {4,2}. For details, reference can be made to a correspondence between asearch space where a UE needs to perform blind detection in a downlinksub-frame and the number of blind detections to be attempted, which isas shown in Table 1 below. The number of attempting blind detectionsindicates the number of PDCCH candidates.

TABLE 1 search space aggregation size of search number of blind typelevel space detections UE-specific search 1 6 6 space 2 12 6 4 8 2 8 162 public search space 4 16 4 8 16 2

Referring to Table 1, it can be seen that the number of CSS searches issix and the number of UCSS searches is 16. In UCSS, a DCI format for aUE at the same moment has only two payload sizes, so search needs to beperformed twice, that is, for 32 times. When a UE performs blinddetection in a PDCCH search space, the UE only needs to attempt todecode a DCI that may occur, and does not need to match all DCI formats.Although a relevant technical specification has not yet been determined,in the NR system, there is a limit to the maximum number of blinddetections.

5. Other Terms

Such term as “and/or” in this specification is only a kind ofassociation relationship describing related objects, and refers to thatthere may be three kinds of relationships. For example, “A and/or B” mayrefer to three cases: A exists alone, both A and B exist simultaneously,and B exists alone. In addition, the symbol “I” in this specificationgenerally indicates that the related objects are in an “or”relationship, while in the formula, the symbol “I” indicates that therelated objects are in a “divide” relationship. If not specified, suchterms as “a plurality of” or “multiple” herein refer to two or more.

In order to clearly describe the technical solutions of embodiments ofthe present disclosure, in the embodiments of the present disclosure,such terms as “first”, “second”, or the like in the specification andclaims of embodiments of the present disclosure are used to distinguishsame objects or similar objects having basically the same functions orapplications. Those skilled in the art may appreciate that such terms as“first”, “second”, or the like are not to limit the number of the objector a performing order of the objects.

In the embodiments of the present disclosure, words such as “exemplary”or “for example” are used as example, illustration or description. Anyembodiment or design scheme described as “exemplary” or “for example” inthe embodiments of the present disclosure should not be construed asmore optional or advantageous than other embodiments or design schemes.More exactly, the use of the words “exemplary” or “for example” areintended to present relevant concepts in a specific manner.

FIG. 5 is a schematic flowchart of a method for monitoring a PDCCHprovided by the present disclosure. The solutions provided byembodiments of the present disclosure are directed to a scenario where anetwork device configures one or more BWPs for a terminal, and theterminal is in a BWP operating mode. The method specifically includessteps S201 to S203.

In step S201, a network device determines configuration information ofat least one control resource set (CORESET).

The at least one CORESET may be configured in a unit of a carrier, ormay be configured in a unit of a bandwidth part (BWP). Specifically, ina case that the at least one CORESET is configured in a unit of acarrier, one carrier is configured with at least one CORESET, and thenumber of CORESETs configured for a carrier may be different from thenumber of CORESETs configured for another carrier, which is not limitedherein. In a case that the at least one CORESET is configured in a unitof a BWP, one BWP is configured with at least one CORESET, the number ofCORESETs configured for a BWP may be different from the number ofCORESETs configured for another BWP, which is not limited herein.

In step S202, the network device transmits the configuration informationof the at least one CORESET to a terminal.

In step S203, the terminal monitors the PDCCH in the at least oneCORESET in accordance with the configuration information of the at leastone CORESET.

The network device configures CORESETs on a carrier or on a BWP for theterminal, and the terminal in a BWP operating mode in a CORESET canperform PDCCH detection in the configured CORESETs that fall within aBWP where the terminal currently operates. Therefore, PDCCH blinddetection can be realized for a terminal in a BWP operating mode.

FIG. 6 is a schematic flowchart of a method for monitoring a PDCCHprovided by the present disclosure. This embodiment is directed to ascenario where a terminal is in a BWP operating mode. When monitoring aPDCCH in at least one CORESET, the terminal needs to determine a CORESETthat needs to be monitored from all configured CORESETs. The process ofdetermining the CORESET that needs to be monitored from the configuredCORESET by the terminal may be specifically implemented by twoimplementation manners. Therefore, based on steps S201 and S203 providedin the above embodiment, in this embodiment, step S203 may be replacedwith step S303 a, or step S203 may be replaced with S303 b 1 and S303 b2 according to different implementation manners.

As shown in FIG. 6, a first manner is an implicit determination method(that is, a terminal implicitly determines a CORESET that needs to bemonitored according to a correspondence between a CORESET and a BWP).

Specifically, step S303 a is substituted for step S203, and the methodincludes: step S303 a. In step S303 a, the terminal monitors, inaccordance with the configuration information of the at least oneCORESET, the PDCCH in at least one complete CORESET and/or at least oneincomplete CORESET within a BWP currently accessed by the terminal.

As shown in FIG. 6, a second manner is an explicit determination method(that is, a base station transmits a signaling instruction to aterminal, to indicate the terminal the CORESET that needs to bemonitored).

Specifically, steps S303 b 1 and S303 b 2 are substituted for step S203,and the method includes: steps S303 b 1 and S303 b 2. In step S303 b 1,the network device transmits first indication information to theterminal, where the first indication information is used to instruct theterminal to monitor at least one complete CORESET and/or at least oneincomplete CORESET within a BWP that the terminal currently accesses.

Exemplarily, a terminal may directly determine which CORESET is selectedto be monitored from pre-configured CORESETs according to a signalinginstruction from the base station. The signaling instruction may be aPDCCH signaling instruction or a MAC CE signaling instruction.

In step S303 b 2, the terminal monitors, based on indication of thefirst indication information, the PDCCH in the at least one completeCORESET and/or the at least one incomplete CORESET within the BWP thatthe terminal currently accesses.

As an example, in a case that the at least one CORESET is configured percarrier, whether a method used to determine a CORESET that needs to bemonitored is the first manner or the second manner as mentioned above, aCORESET falling within a BWP that a terminal is currently accessing maybe a complete CORESET and/or an incomplete CORESET configured for acarrier on which the terminal is currently located. It should be notedthat the incomplete CORESET in the present disclosure does not refer toan imperfect CORESET, but refers to a part of a pre-configured CORESETfrequency-domain resource, that is, only a part of a time-frequencyresource of the complete CORESET are used.

In a first embodiment, in a case that the CORESET(s) is configured basedon a carrier, a terminal determines at least one complete CORESET in aset of CORESETs for a carrier where the terminal is currently located,and monitors a PDCCH in the determined complete CORESET(s), where the atleast one complete CORESET falls within a BWP that is currently accessedby the terminal.

For example, as shown in FIG. 7, CORESETs are configured based on acarrier, and three CORESETs are configured on the carrier (CORESET1,CORESET2, and CORESET3 in FIG. 7). If CORESET1 falls into BWP1 currentlyaccessed by the terminal, and CORESET1 is a complete CORESET, theterminal only needs to monitor CORESET1 that falls into BWP1. In theprocess of determining, by the terminal, a CORESET that needs to bemonitored in BWP1, the terminal may implicitly determine the CORESETaccording to a correspondence between a CORESET and a BWP, that is,determining the CORESET falling within a bandwidth of BWP1, or maydetermine which one of the three pre-configured CORESETs is selected forspecific monitoring based on indication information transmitted by anetwork device

In a second embodiment, in a case that the CORESET(s) is configuredbased on a carrier, a terminal determines at least one incompleteCORESET in a CORESET set for a carrier where the terminal is currentlylocated, and monitors a PDCCH in the determined incomplete CORESET(s),where the at least one incomplete CORESET falls within a BWP that iscurrently accessed by the terminal.

For example, as shown in FIG. 8, CORESETs are configured based on acarrier, and three CORESETs (CORESET1, CORESET2, and CORESET3 in FIG. 8)are configured on the carrier, if part of CORESET1 falls into BWP1currently accessed by the terminal, and CORESET1 is an incompleteCORESET, (referring to FIG. 8, only a part of a time-frequency resourceof CORESET1 falls within a bandwidth of BWP1), the terminal only needsto monitor the part of CORESET1 that falls into BWP1. In the process ofdetermining a CORESET that needs to be monitored in BWP1 by theterminal, the terminal may implicitly determine the CORESET according toa correspondence between a CORESET and a BWP, or may determine which oneof the three pre-configured CORESETs is selected and which part of theone selected CORESET is selected for specific monitoring based onindication information transmitted by a network device.

In a third embodiment, in a case that the CORESET(s) is configured basedon a carrier, a terminal determines that at least one complete CORESETand at least one incomplete CORESET of at least one complete CORESET ina CORESET set for a carrier where the terminal is currently located,where the at least one complete CORESET and the at least one incompleteCORESET fall within the BWP that the terminal currently accesses.

For example, as shown in FIG. 9, CORESETs are configured based on acarrier, and three CORESETs are configured on the carrier (CORESET1,CORESET2, and CORESET3 in FIG. 6). If CORESET1, CORESET2, and CORESET3all fall into BWP1 currently accessed by the terminal, and CORESET1 andCORESET3 that fall into BWP1 are incomplete CORESET (referring to FIG.9, only a part of a time-frequency resource of CORESET1 and only a partof a time-frequency resource of CORESET3 fall within a bandwidth ofBWP1), the terminal needs to monitor the complete CORESET2, and the partof CORESET1 and the part of CORESET3 that fall into BWP1, and of course,the terminal may only monitor any of the three CORESETs. In the processof determining a CORESET that needs to be monitored in BWP1 by theterminal, the terminal may implicitly determine the CORESET according toa correspondence between a CORESET and a BWP, or may determine which oneof the three pre-configured CORESETs is selected or which part of theone CORESET is selected for specific monitoring based on indicationinformation transmitted by a network device.

Exemplarily, in a case that at least one CORESET configured by a networkdevice for a terminal in the present disclosure is configured in a unitof BWP, whether a method used to determine a CORESET that needs to bemonitored is the first manner or the second manner as mentioned above, aCORESET falling within a BWP that a terminal is currently accessing isalways a complete CORESET.

For example, as shown in FIG. 10, CORESETs are configured based on aBWP, and three CORESETs are configured on BWP1 (CORESET1, CORESET2, andCORESET3 in FIG. 10). When a terminal currently accesses BWP1, theterminal may directly select a CORESET from the three CORESETs formonitoring, or may determine which one of the three pre-configuredCORESETs is selected for specific monitoring based on indicationinformation transmitted by a network device

FIG. 11 is a schematic flowchart of a method for monitoring a PDCCHprovided by the present disclosure. This embodiment is directed to ascenario where a terminal is in a BWP operating mode and the terminal isswitched from a first BWP to a second BWP, where the first BWP is a BWPthat is currently accessed and the second BWP is a target BWP. It shouldbe noted that the scenario where the terminal is switched from the firstBWP to the second BWP in this embodiment includes: a BWP switchingscenario and a BWP adjustment scenario (for example, a bandwidth of theBWP that the terminal currently accesses changes, and/or a centerfrequency of the BWP that the terminal currently accesses changes).

When monitoring a PDCCH in at least one CORESET, the terminal needs todetermine a CORESET that needs to be monitored from all configuredCORESETs. The process of determining the CORESET that needs to bemonitored from the configured CORESET by the terminal may bespecifically implemented by two implementation manners. Therefore, basedon steps S201 and S203 provided in the above embodiment, in thisembodiment, step S203 may be replaced with S403 a, or step S203 may bereplaced with steps S403 b 1 and S403 b 2 according to implementationmanners.

As shown in FIG. 11, a first manner is an implicit determination method(that is, a terminal implicitly determines a CORESET that needs to bemonitored according to a correspondence between a CORESET and a BWP).

Specifically, step S203 is replaced with steps S403 a, and the methodincludes: steps S403 a. In step S403 a, the terminal monitors, inaccordance with the configuration information of the at least oneCORESET, the PDCCH in at least one complete CORESET and/or at least oneincomplete CORESET within a second BWP, in a case that the terminal isswitched from a first BWP to the second BWP.

As shown in FIG. 11, a second manner is an explicit determination method(that is, a base station transmits a signaling instruction to aterminal, to indicate the terminal the CORESET that needs to bemonitored).

Specifically, step S203 is replaced with steps S403 b 1 and S403 b 2,and the method includes: steps S403 b 1 and S403 b 2.

In step S403 b 1, the network device transmits first indicationinformation to the terminal, where the first indication information isused to instruct the terminal to monitor at least one complete CORESETand/or at least one incomplete CORESET within the second BWP.

In step S403 b 2, the terminal monitors, based on indication of thefirst indication information, the PDCCH in the at least one completeCORESET and/or the at least one incomplete CORESET within the secondBWP.

Optionally, the at least one CORESET configured by the network devicefor the terminal is configured per carrier.

Exemplarily, the above step S403 a includes: A1, the terminalmonitoring, based on indication of the first indication information, aPDCCH in at least one complete CORESET and/or at least one incompleteCORESET of all CORESETs that correspond to a first carrier, where the atleast one complete CORESET and/or the at least one incomplete CORESETfalls within the second BWP, and the first carrier includes the firstBWP and the second BWP.

Optionally, the first indication information in the above step S403 b 1is used to instruct a terminal to monitor at least one complete CORESETand/or at least one incomplete CORESET among all CORESETs thatcorrespond to a first carrier, where the at least one complete CORESETand/or the at least one incomplete CORESET falls within the second BWP,and the first carrier includes the first BWP and the second BWP.

Specifically, the above S403 b 2 includes: B1, monitoring the PDCCH inat least one CORESET and/or at least one incomplete CORESET among allthe CORESETs that correspond to the first carrier based on indication ofthe first indication information and the configuration information ofthe at least one CORESET, where the at least one complete CORESET and/orthe at least one incomplete CORESET falls within the second BWP.

In a first example as shown in FIG. 12, CORESETs are configured based ona carrier, three CORESETs (CORESET1, CORESET2, CORESET3 in FIG. 12) areconfigured on the carrier, and CORESET1, CORESET2, CORESET3 configuredon the carrier fall into BWP1. When a terminal switches from BWP1 toBWP2, the terminal only monitors CORESET2 that falls into BWP2. In aprocess of determining a CORESET that needs to be monitored in BWP2 bythe terminal, the terminal may implicitly determine the CORESETaccording to a correspondence between CORESETs and BWPs, or may select aCORESET from the three pre-configured CORESETs for specific monitoringbased on indication information transmitted by a network device.

In a second example as shown in FIG. 13, a CORESET is configured basedon a carrier, CORESET1 is configured on the carrier, and CORESET1 fallsinto BWP1. When a terminal switches from BWP1 to BWP2, the terminal onlymonitors a part of CORESET1 that falls within BWP2. In a process ofdetermining a CORESET that needs to be monitored in BWP2 by theterminal, the terminal may implicitly determine the CORESET according toa correspondence between CORESETs and BWPs, or may select a part ofCORESET1 for specific monitoring based on indication informationtransmitted by a network device.

In a third example as shown in FIG. 14, CORESETs are configured based ona carrier, and three CORESETs (CORESET1, CORESET2, and CORESET3 in FIG.14) are configured on the carrier, and CORESET1 configured on thecarrier falls into BWP1. When a terminal switches from BWP1 to BWP2, theterminal only monitors CORESET3 that falls into BWP2. In a process ofdetermining a CORESET that needs to be monitored in BWP2 by theterminal, the terminal may implicitly determine the CORESET according toa correspondence between CORESETs and BWPs, or may select a CORESET fromthe three pre-configured CORESETs for specific monitoring based onindication information transmitted by a network device.

Optionally, at least one CORESET configured by a network device for aterminal is configured per BWP.

Exemplarily, the above step S403 a includes: A2, the terminalmonitoring, in accordance with the configuration information of the atleast one CORESET, a PDCCH in at least one CORESET of all CORESETs thatcorrespond to a second BWP.

Exemplarily, the first indication information in the above step S403 b 1is used to instruct the terminal to monitor at least one CORESET amongall CORESETs corresponding to the second BWP.

Specifically, the above step S403 b 2 includes: B2, monitoring the PDCCHin at least one CORESET among all the CORESETs that correspond to thesecond BWP based on indication of the first indication information andthe configuration information of the at least one CORESET.

In a fourth example as shown in FIG. 15 and FIG. 16, a CORESET isconfigured in BWP1 and BWP2 for a terminal (as shown in FIG. 15 and FIG.16, BWP1 is configured with CORESET1 and BWP2 is configured withCORESET2). After the terminal is switched from BWP1 to BWP2, theterminal only monitors CORESET2 configured for BWP2. In a process ofdetermining a CORESET that needs to be monitored in BWP2 by theterminal, the terminal may implicitly determine the CORESET according toa correspondence between CORESETs and BWPs, or may select a CORESET frompre-configured CORESET1 and CORESET2 for specific monitoring based onindication information transmitted by a network device. As shown in FIG.13, center frequencies of BWP1 and BWP2 are the same. As shown in FIG.14, center frequencies of BWP1 and BWP2 are different. Therefore, whenCORESETs are configured based on a BWP, only a CORESET in a BWP to whichthe terminal has switched needs to be considered for monitoring.

In a fifth example as shown in FIG. 17, three CORESETs are configured inBWP1, and one CORESET is configured in BWP2 for a terminal (as shown inFIG. 17, BWP1 is configured with CORESET1 to CORESET3, and BWP2 isconfigured with CORESET4). When a terminal is switched from BWP1 toBWP2, the terminal only monitors CORESET4 configured for BWP2. In aprocess of determining a CORESET that needs to be monitored in BWP2 bythe terminal, the terminal may implicitly determine the CORESETaccording to a correspondence between CORESETs and BWPs, or may select aCORESET from the pre-configured CORESET1 to CORESET4 for specificmonitoring based on indication information transmitted by a networkdevice.

Optionally, in a case that a terminal switches from a first BWP to asecond BWP, and a network device and the terminal have a vagueunderstanding of the switching time, the following method may be adoptedto ensure service continuity.

Exemplarily, in a case that a PDCCH DCI parameter changes as a bandwidthof a BWP for a terminal changes (that is, a DCI parameter of a first BWPbefore the switching (such as a DCI format or a length of DCI) isdifferent from a DCI parameter of a second BWP after the switching), thecorresponding solution includes at least one of:

C1, the network device transmitting a DCI parameter corresponding to thefirst BWP and a DCI parameter corresponding to the second BWP to theterminal; or

C2, the terminal detecting a DCI parameter corresponding to the secondBWP.

Accordingly, in a case that a location of a BWP that a terminal accesseschanges (that is, a center frequency of the first BWP before theswitching is different from a center frequency of the second BWP afterthe switching), the corresponding solution includes at least one of:

D1, the network device transmitting DCI to the terminal in a CORESETcorresponding to the first BWP, and transmitting DCI to the terminal ina CORESET corresponding to the second BWP; or

D2, detecting, within the second BWP, DCI transmitted by a networkdevice in a CORESET corresponding to the second BWP.

In this way, when a bandwidth of a BWP for a terminal changes, and anetwork device has ambiguous understanding of the switching time, thenetwork device transmits a DCI parameter of a BWP before the switchingand a DCI parameter of a BWP after the switching, so that the terminalcan receive the DCI parameter of the BWP after the switching, therebyensuring that the terminal can successfully receive DCI when monitoringa PDCCH in the BWP. Similarly, when a location of a BWP for a terminalchanges, and a network device has ambiguous understanding of theswitching time, the network device schedules the terminal bytransmitting DCI in CORESETs corresponding to two BWPs before and afterthe switching, thereby ensuring that the terminal receives DCI in aCORESET of the BWP after the switching.

It should be noted that when a bandwidth of a BWP for a terminal and alocation of a BWP for a terminal are both changed, the above steps C1and C2, and the above steps D1 and D2 need to be performed.

The solutions provided by the embodiments of the present disclosure aredescribed above mainly from the perspective of interaction between anetwork device and a terminal. It can be understood that, in order toimplement the above functions, each network device or each terminalincludes a hardware structure and/or a software module used to achieve acorresponding function. A person of ordinary skill in the art shouldeasily realize that, in combination with the units and algorithm stepsof the examples described in the embodiments of the present disclosure,the embodiments of the present disclosure can be implemented in the formof hardware or in the form of hardware combined with computer software.Whether a certain function is performed by hardware or computer softwaredriven by hardware depends on specific applications and designconstraints of a technical solution. A person skilled in the art canimplement the described functions by using different methods for variousspecific applications, but such implementations should not be consideredbeyond the scope of the present application.

In the embodiments of the present disclosure, functional modules of anetwork device, a terminal, and the like can be divided according to theabove method embodiments. For example, functional modules may be dividedto correspond to respective functions, or two or more functions may beintegrated into one processing module. The above integrated modules canbe implemented in a form of hardware or software functional modules. Itshould be noted that the division of modules in the embodiments of thepresent disclosure is exemplary, and is only a logical functiondivision. There may be other division manners in actual implementations.

In a case that functional modules are divided according to variousfunctions, FIG. 18 illustrates a possible structural diagram of anetwork device provided by the present disclosure. As shown in FIG. 18,a network device 500 may include: a determination unit 501 and atransmission unit 502.

The determination unit 501 is configured to determine configurationinformation of at least one control resource set (CORESET).

The transmission unit 502 is configured to transmit the configurationinformation of the at least one CORESET to a terminal; where the atleast one CORESET is configured per carrier or per bandwidth part (BWP),and the carrier includes at least one BWP. In a case that the at leastone CORESET is configured per carrier, one carrier is configured with atleast one CORESET; and in a case that the at least one CORESET isconfigured per BWP, one BWP is configured with at least one CORESET.

Optionally, the transmission unit 502 is further configured to transmitfirst indication information to the terminal, and the first indicationinformation is used to instruct the terminal to monitor at least onecomplete CORESET and/or at least one incomplete CORESET within a BWPthat the terminal currently accesses.

Further optionally, in a case that the terminal is switched from a firstBWP to a second BWP, the first indication information is used toinstruct the terminal to monitor at least one complete CORESET and/or atleast one incomplete CORESET within the second BWP.

Further optionally, in a case that the at least one CORESET isconfigured per carrier, the first indication information is used toinstruct the terminal to monitor at least one complete CORESET and/or atleast one incomplete CORESET of all CORESETs that correspond to a firstcarrier, the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP, and the first carrierincludes the first BWP and the second BWP; or in a case that the atleast one CORESET is configured per BWP, the first indicationinformation is used to instruct the terminal to monitor at least oneCORESET of all CORESETs corresponding to the second BWP.

Optionally, the transmission unit 502 is further configured to, in acase that the terminal is switched from a first BWP to a second BWP,transmit, to the terminal, a downlink control information (DCI)parameter corresponding to the first BWP and a DCI parametercorresponding to the second BWP, when the DCI parameter of the first BWPis different from the DCI parameter of the second BWP; and/or transmit,to the terminal, DCI in a CORESET corresponding to the first BWP, andtransmitting, to the terminal, DCI in a CORESET corresponding to thesecond BWP, when a center frequency of the first BWP is different from acenter frequency of the second BWP.

Optionally, the configuration information of each of the at least oneCORESET includes at least one of: time-frequency resource information ofthe CORESET, a set of aggregation levels to be monitored in the CORESET,the number of PDCCH candidates to be monitored at each aggregation levelin the CORESET, or a DCI parameter of a PDCCH to be monitored in theCORESET.

It should be noted that all relevant content of steps involved in theforegoing method embodiments can be applicable to functionaldescriptions of corresponding functional modules, which are not berepeated herein.

An embodiment of the present disclosure further provides a networkdevice, including a processor, a memory, and a computer program storedon the memory and executable on the processor. The computer program isexecuted by the processor to implement processes of the method formonitoring the PDCCH in the above embodiments, and can achieve the sametechnical effects. To avoid repetition, details are not described hereinagain.

An embodiment of the present disclosure further provides acomputer-readable storage medium. A computer program is stored on thecomputer-readable storage medium, and the computer program is executedby a processor to implement processes of the method for monitoring aPDCCH in the above embodiments, and can achieve the same technicaleffects. To avoid repetition, details are not described herein again.The computer-readable storage medium is, for example, a read-only memory(ROM), a random access memory (RAM), a magnetic disk or an optical disk.

In case of using an integrated unit, an embodiment of the presentdisclosure further provides a network device, such as a base station.FIG. 19 is a structural diagram of a network device applied in anembodiment of the present disclosure, which can implement the details ofthe method in the above embodiments, can achieve the same technicaleffects. As shown in FIG. 19, a network device 600 includes: a processor601, a transceiver 602, a memory 603 and a bus interface.

In an embodiment of the present disclosure, the network device 600further includes a computer program stored in the memory 603 andexecutable on the processor 601. The computer program is executed by theprocessor 601 to implement the following steps:

a first step, determining configuration information of at least onecontrol resource set (CORESET); and

a second step, transmitting the configuration information of the atleast one CORESET to a terminal, where the at least one CORESET isconfigured per carrier or per bandwidth part (BWP), and the carrierincludes at least one BWP, in a case that the at least one CORESET isconfigured per carrier, one carrier is configured with at least oneCORESET; and in a case that the at least one CORESET is configured perBWP, one BWP is configured with at least one CORESET.

In FIG. 19, a bus architecture may include any number of interconnectedbuses and bridges, and may be specifically configured to couple variouscircuits including one or more processors represented by the processor601 and storages represented by the memory 603. The bus architecture mayalso couple various other circuits such as peripherals, voltageregulators and power management circuits, which are well known in theart. Therefore, a detailed description thereof is omitted herein. A businterface provides an interface. The transceiver 602 may be multipleelements, i.e., including a transmitter and a receiver, to allow forcommunication with various other apparatuses on the transmission medium.The processor 601 is responsible for supervising the bus architectureand normal operation and the memory 603 may store the data used by theprocessor 601 during operation.

The processor 601 is responsible for managing the bus architecture andgeneral processing, and the memory 603 may store data used by theprocessor 601 when performing operations.

Optionally, the computer program is executed by the processor 601 toimplement the following steps:

a third step, transmitting first indication information to the terminal,where the first indication information is used to instruct the terminalto monitor at least one complete CORESET and/or at least one incompleteCORESET within a BWP that the terminal currently accesses.

Optionally, in a case that the terminal is switched from a first BWP toa second BWP, the first indication information is used to instruct theterminal to monitor at least one complete CORESET and/or at least oneincomplete CORESET within the second BWP.

Further optionally, in a case that the at least one CORESET isconfigured per carrier, the first indication information is used toinstruct the terminal to monitor at least one complete CORESET and/or atleast one incomplete CORESET of all CORESETs that correspond to a firstcarrier, where the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP, and the first carrierincludes the first BWP and the second BWP; or in a case that the atleast one CORESET is configured per BWP, the first indicationinformation is used to instruct the terminal to monitor at least oneCORESET of all CORESETs corresponding to the second BWP

Optionally, in a case that the terminal is switched from a first BWP toa second BWP, the computer program is executed by the processor 601 tofurther implement the following steps:

a fourth step, transmitting, to the terminal, a downlink controlinformation (DCI) parameter corresponding to the first BWP and a DCIparameter corresponding to the second BWP, when the DCI parameter of thefirst BWP is different from the DCI parameter of the second BWP; and/or

a fifth step, transmitting, to the terminal, DCI in a CORESETcorresponding to the first BWP, and transmitting, to the terminal, DCIin a CORESET corresponding to the second BWP, when a center frequency ofthe first BWP is different from a center frequency of the second BWP.

Optionally, the configuration information of each of the at least oneCORESET includes at least one of: time-frequency resource information ofthe CORESET, a set of aggregation levels to be monitored, the number ofPDCCH candidates at each aggregation level to be monitored, or a DCIparameter of a PDCCH to be monitored in the CORESET.

For the analysis of the related content of the above first to fifthsteps, reference may be made to the foregoing method embodiments, anddetails are not described herein again. In addition, the network devicecan implement the processes implemented by the network device in theforegoing embodiments. To avoid repetition, details are not describedherein again. It should be noted that the present disclosure does notlimit the sequence of the above steps performed by the network device.The execution order of the above steps should be determined by functionsand internal logics of corresponding steps, that is, the sequence numberof the above steps should not limit implementation processes in theembodiments of the present disclosure.

In the embodiments of the present disclosure, a network deviceconfigures one or more CORESETs for a terminal by transmittingconfiguration information of at least one CORESET to the terminal. Theat least one CORESET may be configured by using a carrier as a unit orusing a BWP as a unit. When operating in a BWP operating mode, theterminal selects a CORESET that needs to be monitored frompre-configured CORESETs, and monitors a PDCCH in the CORESET that needsto be monitored in accordance with the configuration information of atleast one CORESET. Therefore, PDCCH blind detection can be realized fora terminal in a BWP operating mode.

In a case that functional modules are divided according to variousfunctions, FIG. 20 shows a possible structural diagram of a terminalprovided by the present disclosure. As shown in FIG. 20, a terminal 700may include a reception unit 701 and a monitoring unit 702.

The reception unit 701 is configured to receive configurationinformation of at least one control resource set (CORESET), where the atleast one CORESET is configured per carrier or per bandwidth part (BWP),and the carrier includes at least one BWP; in a case that the at leastone CORESET is configured per carrier, one carrier is configured with atleast one CORESET; and in a case that the at least one CORESET isconfigured per BWP, one BWP is configured with at least one CORESET.

The monitoring unit 702 is configured to monitor a physical downlinkcontrol channel (PDCCH) in the at least one CORESET in accordance withthe configuration information of the at least one CORESET.

Optionally, the monitoring unit 702 is specifically configured tomonitor the PDCCH in at least one complete CORESET and/or at least oneincomplete CORESET within a BWP currently accessed by the terminal.

Further optionally, the monitoring unit 702 is specifically configuredto monitor the PDCCH in at least one complete CORESET and/or at leastone incomplete CORESET within a second BWP, in a case that the terminalis switched from a first BWP to the second BWP.

Further optionally, in a case that the terminal is switched from a firstBWP to a second BWP, the monitoring unit 702 is specifically configuredto:

monitor the PDCCH in at least one complete CORESET and/or at least oneincomplete CORESET of all CORESETs that correspond to a first carrier,where the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP, in a case that the atleast one CORESET is configured per carrier, where the first carrierincludes the first BWP and the second BWP; or

monitor the PDCCH in at least one CORESET of all CORESETs correspondingto the second BWP, in a case that the at least one CORESET is configuredper BWP.

Optionally, as shown in FIG. 20, the terminal 700 further includes: areception unit 703. The reception unit 703 is configured to receivefirst indication information transmitted by the terminal, and the firstindication information is used to instruct the terminal to monitor atleast one complete CORESET and/or at least one incomplete CORESET withina BWP that the terminal currently accesses. The monitoring unit 702 isfurther configured to monitor, based on indication of the firstindication information, the PDCCH in the at least one complete CORESETand/or the at least one incomplete CORESET within the BWP that theterminal currently accesses.

Further optionally, in a case where the terminal is switched from afirst BWP to a second BWP, and when the first indication information isused to instruct the terminal to monitor at least one complete CORESETand/or at least one incomplete CORESET within the second BWP, themonitoring unit 702 is specifically configured to monitor, based onindication of the first indication information, the PDCCH in the atleast one complete CORESET and/or the at least one incomplete CORESETwithin the second BWP.

Further optionally, in a case that the at least one CORESET isconfigured per carrier, the first indication information is used toinstruct the terminal to monitor at least one complete CORESET and/or atleast one incomplete CORESET of all CORESETs that correspond to a firstcarrier, where the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP. The monitoring unit 702is specifically configured to: monitor, based on indication of the firstindication information, the PDCCH in the at least one complete CORESETand/or the at least one incomplete CORESET of all the CORESETs thatcorrespond to the first carrier and fall within the second BWP, wherethe first carrier includes the first BWP and the second BWP; or in acase that the at least one CORESET is configured per BWP, the firstindication information is used to instruct the terminal to monitor atleast one CORESET of all CORESETs corresponding to the second BWP, andthe monitoring unit is specifically configured to monitor, based onindication of the first indication information, the PDCCH in the atleast one CORESET of all the CORESETs corresponding to the second BWP.

Optionally, in a case that the terminal is switched from a first BWP toa second BWP, the terminal 700 further includes a detection unit 704.The detection unit 704 is further configured to detect a downlinkcontrol information (DCI) parameter corresponding to the second BWP,when a DCI parameter of the first BWP is different from the DCIparameter of the second BWP; and/or, detect, within the second BWP, DCItransmitted by a network device in a CORESET corresponding to the secondBWP, when a center frequency of the first BWP is different from a centerfrequency of the second BWP.

Optionally, the configuration information of each of the at least oneCORESET includes at least one of: time-frequency resource information ofthe CORESET, a set of aggregation levels to be monitored, the number ofPDCCH candidates at each aggregation level to be monitored, or a DCIparameter of a PDCCH to be monitored in the CORESET.

It should be noted that all relevant content of steps involved in theforegoing method embodiments can be applicable to functionaldescriptions of corresponding functional modules, which are not berepeated herein.

An embodiment of the present disclosure further provides a networkdevice, including a processor, a memory, and a computer program storedon the memory and executable on the processor. The computer program isexecuted by the processor to implement processes of the method formonitoring a PDCCH in the above embodiments, and can achieve the sametechnical effects. To avoid repetition, details are not described hereinagain.

An embodiment of the present disclosure further provides acomputer-readable storage medium. A computer program is stored on thecomputer-readable storage medium, and the computer program is executedby a processor to implement processes of the method for monitoring aPDCCH in the above embodiments, and can achieve the same technicaleffects. To avoid repetition, details are not described herein again.The computer-readable storage medium is, for example, a read-only memory(ROM), a random access memory (RAM), a magnetic disk or an optical disk.

In case of using an integrated unit, an embodiment of the presentdisclosure further provides a terminal. FIG. 21 is a block diagram of aterminal according to another embodiment of the present disclosure. Aterminal 800 shown in FIG. 21 includes: at least one processor 801, amemory 802, and at least one network interface 803. Various componentsin the terminal 800 are coupled to each other via a bus system 804. Itis understood that that the bus system 804 is configured to enableconnections and communications among these components. In addition tothe data bus, the bus system 804 includes a power bus, a control bus anda status signal bus. For clarity, various buses are all labeled as thebus system 804 in FIG. 21.

It is understood that, the memory 802 provided by embodiments of thepresent disclosure may be a volatile or non-volatile storage, or mayinclude both of the volatile and non-volatile storages. The non-volatilestorage may be a read-only memory (ROM), a programmable ROM (PROM), anerasable PROM (EPROM), an electrically EPROM (EEPROM) or a flash memory.The volatile storage may be a random access memory (RAM), which is usedas an external cache. By way of example and without any limitation, manyforms of RAMs may be used, such as static RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM) and direct Rambus RAM(DRRAM). The memory 802 of the system and method described herein ismeant to include, without limitation, these and any other suitable typesof storages.

In some implementations, the memory 802 stores following elements:executable module or data structure, or a subset or extension setthereof, such as an operating system 8021 and an application 8022.

The operating system 8021 includes various system programs, such asframework layer programs, core library layer programs and driver layerprograms, to implement various fundamental services and processhardware-based tasks. The application 8022 includes variousapplications, such as media player and browser, to implement a varietyof application services. The program implementing the method accordingto embodiments of the present disclosure may be included in theapplication 8022.

In embodiments of the present disclosure, the terminal 800 may include:a computer program stored in the memory 802 and executable by theprocessor 801. The computer program is configured to be executed by theprocessor 801 to implement following steps:

a first step, receiving configuration information of at least onecontrol resource set (CORESET), where the at least one CORESET isconfigured per carrier or per bandwidth part (BWP), and the carrierincludes at least one BWP; in a case that the at least one CORESET isconfigured per carrier, one carrier is configured with at least oneCORESET; and in a case that the at least one CORESET is configured perBWP, one BWP is configured with at least one CORESET; and

a second step, monitoring the PDCCH in the at least one CORESET inaccordance with the configuration information of the at least oneCORESET.

The method disclosed in the foregoing embodiments of the presentdisclosure may be applied to the processor 801 or implemented by theprocessor 801. The processor 801 may be an integrated circuit withsignal processing capability. During an implementation process, steps ofthe methods may be realized in form of hardware by integrated logicalcircuits in the processor 801, or in form of software by instructions.The processor 801 may be a general purpose processor, digital signalprocessor (DSP), application specific integrated circuit (ASIC), fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic device, discrete hardware transistorlogic device, discrete hardware component, that is capable ofimplementing or executing the various methods, steps and logic blockdiagrams disclosed in the embodiments of the present disclosure. Thegeneral purpose processor may be a microprocessor, or any conventionalprocessor, etc. The steps of the methods disclosed with reference to theembodiments of the present disclosure may be embodied in hardware in theform of a coding processor, or performed by the hardware in the codingprocessor and the software modules in combination. The software modulesmay reside in well-established storage medium in the art, such as a RAM,flash memory, ROM, PROM or EEPROM, register, etc. The storage mediumresides in the memory 802. The processor 801 reads information from thememory 802 and performs the steps of the methods with its hardware.

It is understood that, the embodiments described in the presentdisclosure may be implemented by hardware, software, firmware,middleware, microcode or a combination thereof. For hardwareimplementation, processing units may be implemented in one or moreapplication specific integrated circuits (ASIC), digital signalprocessor (DSP), DSP device (DSPD), programmable logic device (PLD),field-programmable gate array (FPGA), general purpose processor,controller, microcontroller, microprocessor, other electronic unitconfigured to perform the function described in this application or acombination thereof.

For software implementation, the technical solutions described in theembodiments of the present disclosure may be implemented by a module(e.g., process, function, etc.) configured to perform the functiondescribed in the embodiments of the present disclosure. Software codemay be stored in a memory and executed by the processor. The memory maybe implemented internal or external to the processor.

In specific, the computer program is configured to be executed by theprocessor 801 to implement following step:

a third step: monitoring, in accordance with the configurationinformation of the at least one CORESET, the PDCCH in at least onecomplete CORESET and/or at least one incomplete CORESET within a BWPcurrently accessed by the terminal.

Further optionally, the above third step specifically includes thefollowing: a four step, monitoring, in accordance with the configurationinformation of the at least one CORESET, the PDCCH in at least onecomplete CORESET and/or at least one incomplete CORESET within a secondBWP, in a case that the terminal is switched from a first BWP to thesecond BWP.

Further optionally, the above fourth step specifically includes:

monitoring the PDCCH in at least one complete CORESET and/or at leastone incomplete CORESET of all CORESETs that correspond to a firstcarrier, where the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP, in a case that the atleast one CORESET is configured per carrier, where the first carrierincludes the first BWP and the second BWP; or

monitoring the PDCCH in at least one CORESET of all CORESETscorresponding to the second BWP, in a case that the at least one CORESETis configured per BWP.

Optionally, the computer program is configured to be executed by theprocessor 801 to implement the following steps:

a fifth step, receiving first indication information transmitted by theterminal, where the first indication information is used to instruct theterminal to monitor at least one complete CORESET and/or at least oneincomplete CORESET within a BWP that the terminal currently accesses;and

a sixth step, monitoring, based on indication of the first indicationinformation, the PDCCH in the at least one complete CORESET and/or theat least one incomplete CORESET within the BWP that the terminalcurrently accesses.

Further, in a case where the terminal is switched from a first BWP to asecond BWP, when the first indication information is used to instructthe terminal to monitor at least one complete CORESET and/or at leastone incomplete CORESET within the second BWP, the above sixth stepincludes the following step:

a seventh step: monitoring, based on indication of the first indicationinformation, the PDCCH in the at least one complete CORESET and/or theat least one incomplete CORESET within the second BWP.

Further, in a case that the at least one CORESET is configured percarrier, the first indication information is used to instruct theterminal to monitor at least one complete CORESET and/or at least oneincomplete CORESET of all CORESETs that correspond to a first carrier,where the at least one complete CORESET and/or the at least oneincomplete CORESET falls within the second BWP, and the seventh stepabove specifically includes:

monitoring, based on indication of the first indication information, thePDCCH in the at least one complete CORESET and/or the at least oneincomplete CORESET of all the CORESETs that correspond to the firstcarrier and fall within the second BWP, where the first carrier includesthe first BWP and the second BWP; or

in a case that the at least one CORESET is configured per BWP, the firstindication information is used to instruct the terminal to monitor atleast one CORESET of all CORESETs corresponding to the second BWP, andthe seventh step above specifically includes:

monitoring, based on indication of the first indication information, thePDCCH in the at least one CORESET of all the CORESETs corresponding tothe second BWP.

Optionally, in a case that the terminal is switched from a first BWP toa second BWP, the computer program is configured to be executed by theprocessor 801 to further implement following step:

an eighth step, detecting a downlink control information (DCI) parametercorresponding to the second BWP, when a DCI parameter of the first BWPis different from the DCI parameter of the second BWP; and/or,detecting, within the second BWP, DCI transmitted by a network device ina CORESET corresponding to the second BWP, when a center frequency ofthe first BWP is different from a center frequency of the second BWP.

Optionally, the configuration information of each of the at least oneCORESET includes at least one of: time-frequency resource information ofthe CORESET, a set of aggregation levels at which a PDCCH requires to beblindly detected in the CORESET, the number of PDCCH candidate resourceson which a PDCCH requires to be blindly detected in the CORESET at eachaggregation level, or a DCI parameter of a PDCCH that requires blinddetection in the CORESET.

For the analysis of the related content of the above first to seventhsteps, reference may be made to the foregoing method embodiments, anddetails are not described herein again. In addition, the terminal 800can implement the processes implemented by the terminal in the foregoingembodiments. To avoid repetition, details are not described hereinagain. It should be noted that the present disclosure does not limit asequence of the above steps performed by the terminal, and the executionsequence of the above steps should be determined by functions andinternal logics of respective steps, that is, the sequence number of theabove steps should not constitute any limitation to implementationprocesses of the embodiments of the present disclosure.

In the embodiment of the present disclosure, after a terminal isconfigured with one or more CORESETs, the one or more CORESETs can beconfigured per carrier or per BWP. When the terminal operates in a BWPoperating mode, the terminal can select a CORESET that needs to bemonitored from the pre-configured CORESET(s) in accordance withconfiguration information of at least one CORESET transmitted by anetwork device, and can monitor a PDCCH in the CORESET that needs to bemonitored in accordance with configuration information of at least oneCORESET. Therefore, a terminal can achieve PDCCH blind detection in aBWP operating mode.

Those skilled in the art should appreciate that the embodiments of thepresent disclosure may be provided as a method, a system, or a computerprogram product. Therefore, the embodiments of the present disclosuremay take forms of an entirely hardware embodiment, an entirely softwareembodiment, or an embodiment combining software and hardware. Moreover,the embodiments of the present disclosure may take the form of acomputer program product implemented on one or more computer availablestorage media (including but not limited to disk storage, CD-ROM,optical storage), which include computer available program codes.

Embodiments of the present disclosure are described with reference toflowcharts and/or block diagrams of methods, devices (systems), andcomputer program products according to embodiments of the presentdisclosure. It should be understood that each process and/or each blockin the flowcharts and/or the block diagrams, and combinations thereofcan be implemented by computer program instructions. These computerprogram instructions may be provided to a processor of a general-purposecomputer, a special-purpose computer, an embedded processor, or otherprogrammable data processing device to produce a machine, so that theinstructions generated by the processor of the computer or otherprogrammable data processing device are used to generate instructionmeans for implementing the functions specified in one or more flows ofthe flowcharts and/or one or more blocks of the block diagrams.

These computer program instructions may also be stored in acomputer-readable memory capable of directing a computer or otherprogrammable data processing device to work in a specific manner, suchthat the instructions stored in the computer-readable memory produce amanufactured article including an instruction device. The instructiondevice implements functions specified in one or more flows of aflowchart and/or one or more blocks of a block diagram.

These computer program instructions can also be loaded onto a computeror other programmable data processing device, so that a series of stepscan be performed on the computer or the other programmable device toproduce a computer-implemented process. The instructions can be executedon the computer or other programmable device to implement steps andfunctions specified in one or more flows of a flowchart and/or one ormore blocks of a block diagram.

Obviously, those skilled in the art can make various modifications andvariations to the embodiments of the present disclosure withoutdeparting from the scope of the present disclosure. In this way, thepresent disclosure shall also intend to include these modifications andvariations of the embodiments of the present disclosure falling withinthe scope of claims of the present disclosure and their equivalenttechnologies.

What is claimed is:
 1. A method for monitoring a physical downlinkcontrol channel (PDCCH), applied to a network device, and comprising:determining configuration information of at least one control resourceset (CORESET); and transmitting the configuration information of the atleast one CORESET to a terminal, wherein the at least one CORESET isconfigured or per bandwidth part (BWP), and one BWP is configured withat least one CORESET; wherein in a case that the terminal is switchedfrom a first BWP to a second BWP, the method further comprises:transmitting, to the terminal, a downlink control information (DCI)parameter corresponding to the first BWP and a DCI parametercorresponding to the second BWP, when the DCI parameter of the first BWPis different from the DCI parameter of the second BWP; and/ortransmitting to the terminal, DCI in a CORESET corresponding to thefirst BWP, and transmitting, to the terminal, DCI in a CORESETcorresponding to the second BWP, when a center frequency of the firstBWP is different from a center frequency of the second BWP.
 2. Themethod according to claim 1, further comprising: transmitting firstindication information to the terminal, wherein the first indicationinformation is used to instruct the terminal to monitor at least onecomplete CORESET and/or at least one incomplete CORESET within a BWPthat the terminal currently accesses.
 3. The method according to claim2, wherein in a case that the terminal is switched from a first BWP to asecond BWP, the first indication information is used to instruct theterminal to monitor at least one complete CORESET and/or at least oneincomplete CORESET within the second MVP.
 4. The method according toclaim 3, wherein the first indication information is used to instructthe terminal to monitor at least one CORESET of all CORESETscorresponding to the second BWP.
 5. The method according to claim 1,wherein the configuration information of each of the at least oneCORESET comprises at least one of: time-frequency resource informationof the CORESET, a set of aggregation levels to be monitored, the numberof PDCCH candidates at each aggregation level to be monitored, or a ICIparameter of a PDCCH to be monitored in the CORESET.
 6. A method formonitoring a physical downlink control channel (PDCCH), applied to aterminal, and comprising: receiving configuration information of atleast one control resource set (CORESET), wherein the at least oneCORESET is configured per bandwidth part (BWP), and one BWP isconfigured with at least one CORESET; and monitoring the PDCCH in the atleast one CORESET in accordance with the configuration information ofthe at least one CORESET; wherein in a case that the terminal isswitched from a first BWP to a second BWP, the method further comprises:detecting a downlink control information (DCI) parameter correspondingto the second BWP, when a DCI parameter of the first BWP is differentfrom the DCI parameter of the second BWP; and/or detecting, within thesecond BWP, DCI transmitted by a network device in a CORSETcorresponding to the second BWP, when a center frequency of the firstBWP is different from a center frequency of the second BWP.
 7. Themethod according to claim 6, wherein the monitoring the PDCCH in the atleast one CORESET comprises: monitoring the PDCCH in at least onecomplete CORESET and/or at least one incomplete CORESET within a BWPcurrently accessed by the terminal.
 8. The method according to claim 7,wherein the monitoring the PDCCH in the at least one complete CORESETand/or the at least one incomplete CORESET within the BWP currentlyaccessed by the terminal comprises: monitoring the PDCCH in at least onecomplete CORESET and/or at least one incomplete CORESET within a secondBWP, in a case that the terminal is switched from a first BWP to thesecond BWP.
 9. The method according to claim 8, wherein the monitoringthe PDCCH in the at least one complete CORESET and/or the at least oneincomplete CORESET within the second BWP comprises: monitoring the PDCCHin at least one CORESET of all CORESETs corresponding to the second BWP.10. The method according to claim 6, further comprising: receiving firstindication information transmitted by the terminal, wherein the firstindication information is used to instruct the terminal to monitor atleast one complete CORESET and/or at least one incomplete CORESET withina BWP that the terminal currently accesses; and monitoring, based onindication of the first indication information, the PDCCH in the atleast one complete CORESET and/or the at least one incomplete CORESETwithin the BWP that the terminal currently accesses.
 11. The methodaccording to claim 10, wherein, in a case Where the terminal is switchedfrom a first BWP to a second BWP, the first indication information isused to instruct the terminal to monitor at least one complete CORESETand/or at least one incomplete CORESET within the second BWP, and themonitoring, based on indication of the first indication information, thePDCCH in the at least one complete CORESET and/or the at least oneincomplete CORESET within the BWP that the terminal currently accessescomprises: monitoring, based on indication of the first indicationinformation, the PDCCH in the at least one complete CORESET and/or theat least one incomplete CORESET within the second BWP.
 12. The methodaccording to claim 11, wherein the first indication information is usedto instruct the terminal to monitor at least one CORESET of all CORESETscorresponding to the second BWP, and the monitoring, based on indicationof the first indication information, the PDCCH in the at least onecomplete CORESET and/or the at least one incomplete CORESET within theBWP that the terminal currently accesses comprises: monitoring, based onindication of the first indication information, the PDCCH in the atleast one CORESET of all the CORESETs corresponding to the second BWP.13. The method according to claim 6, wherein the configurationinformation of each of the at least one CORESET comprises at least oneof: time-frequency resource information of the CORESET, a set ofaggregation levels to be monitored, the number of PDCCH candidates ateach aggregation level to be monitored, or a DCI parameter of a PDCCH tobe monitored in the CORESET.
 14. A network device, comprising aprocessor, a memory, and a program that is stored on the memory andexecutable on the processor, wherein when executing the program, theprocessor is configured to: determine configuration information of atleast one control resource set (CORESET); and transmit the configurationinformation of the at least one CORESET to a terminal; wherein the atleast one CORESET is configured per bandwidth part (BWP), and one BWP isconfigured with at least one CORESET; wherein in a case that theterminal is switched from a first BWP to second BWP, the processor isconfigured to: transmit, to the terminal, a downlink control information(DCI) parameter corresponding to the first BWP and a DCI parametercorresponding to the second BWP, when the DCI parameter of the first BWPis different from the DCI parameter of the second BWP; and/or transmit,to the terminal, DCI in a CORESET corresponding to the first BWP, andtransmitting, to the terminal, DCI in a CORESET corresponding to thesecond BWP, when a center frequency of the first BWP is different from acenter frequency of the second BWP.
 15. The network device according toclaim 14, wherein the processor is further configured to transmit firstindication information to the terminal, and the first indicationinformation is used to instruct the terminal to monitor at least onecomplete CORESET and/or at least one incomplete CORESET within a BWPthat the terminal currently accesses.
 16. The network device accordingto claim 15, wherein in a case that the terminal is switched from afirst BWP to a second BWP, the first indication information is used toinstruct the terminal to monitor at least one complete CORESET and/or atleast one incomplete CORESET within the second BWP.
 17. The networkdevice according to claim 16, wherein the first indication informationis used to instruct the terminal to monitor at least one CORESET of allCORESETs corresponding to the second BWP.
 18. The network deviceaccording to claim 14, wherein the configuration information of each ofthe at least one CORESET comprises at least one of: time-frequencyresource information of the CORESET, a set of aggregation levels to bemonitored, the number of PDCCH candidates at each aggregation level tobe monitored, or a DCI parameter of a PDCCH to be monitored in theCORESET.